Mobility Management Function Determination for Allowed Network Slices of Wireless Device

ABSTRACT

A network function receives, from a radio access network (RAN), a message indicating a wireless device identifier of a wireless device, one or more requested network slices requested by the wireless device, isolation of the one or more requested network slices from one or more other network slices, and access and mobility management function (AMF) discovery. The network function sends, to a unified data management (UDM), a subscriber data request message indicating the wireless device identifier and the one or more requested network slices. The network function receives, from the UDM, a subscriber data response message indicating one or more allowed network slices that the wireless device is allowed to access. The network function determines, based on the network slice isolation information, an address of an AMF that serves the one or more allowed network slices and does not serve the one or more other network slices.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/091,724, filed on Nov. 6, 2020, which is a continuation of U.S.patent application Ser. No. 16/189,454, filed Nov. 13, 2018, whichclaims the benefit of U.S. Provisional Application No. 62/585,830, filedNov. 14, 2017, all of which are hereby incorporated by reference intheir entireties.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1 is a diagram of an example 5G system architecture as per anaspect of an embodiment of the present disclosure.

FIG. 2 is a diagram of an example 5G System architecture as per anaspect of an embodiment of the present disclosure.

FIG. 3 is a system diagram of an example wireless device and a networknode in a 5G system as per an aspect of an embodiment of the presentdisclosure.

FIG. 4 is a system diagram of an example wireless device as per anaspect of an embodiment of the present disclosure.

FIG. 5 depicts two registration management state models in UE 100 andAMF 155 as per an aspect of an embodiment of the present disclosure.

FIG. 6 depicts two connection management state models in UE 100 and AMF155 as per an aspect of an embodiment of the present disclosure.

FIG. 7 is diagram for classification and marking traffic as per anaspect of an embodiment of the present disclosure.

FIG. 8 and FIG. 9 are example call flows for UE registration procedureas per an aspect of an embodiment of the present disclosure.

FIG. 10 is an example diagram of control plane interfaces for networkslicing as per an aspect of an embodiment of the present disclosure.

FIG. 11 is an example diagram depicting UEs assigned to core part of NSIas per an aspect of an embodiment of the present disclosure.

FIG. 12 is an example diagram depicting network slice architecture withtwo groups-common CP NFs and dedicated CP NFs as per an aspect of anembodiment of the present disclosure.

FIG. 13 is an example diagram depicting multiple slices per UE as per anaspect of an embodiment of the present disclosure.

FIG. 14 is an example call flow diagram as per an aspect of anembodiment of the present disclosure.

FIG. 15 is an example call flow diagram as per an aspect of anembodiment of the present disclosure.

FIG. 16 is an example call flow diagram as per an aspect of anembodiment of the present disclosure.

FIG. 17 is an example call flow diagram as per an aspect of anembodiment of the present disclosure.

FIG. 18 is an example call flow diagram as per an aspect of anembodiment of the present disclosure.

FIG. 19 is an example call flow diagram as per an aspect of anembodiment of the present disclosure.

FIG. 20 is an example call flow diagram as per an aspect of anembodiment of the present disclosure.

FIG. 21 is a table illustrating an aspect of an embodiment of thepresent disclosure.

FIG. 22 is a table illustrating an aspect of an embodiment of thepresent disclosure.

FIG. 23 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 24 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present invention enable implementation ofenhanced features and functionalities in 5G systems. Embodiments of thetechnology disclosed herein may be employed in the technical field of 5Gsystems and network slicing for communication systems. Moreparticularly, the embodiments of the technology disclosed herein mayrelate to 5G core network and 5G systems for AMF Selection for IsolatedNetwork Slice in communication systems. Throughout the presentdisclosure, UE, wireless device, and mobile device are usedinterchangeably. Throughout the present disclosure, base station,(Radio) Access Network ((R)AN), Next Generation Radio Access Network(NG-RAN), New radio Node B (gNB), Next Generation eNodeB (ng-eNBs) areused interchangeably. The following acronyms are used throughout thepresent disclosure:

-   -   5G 5th generation mobile networks    -   5GC 5G Core Network    -   5GS 5G System    -   5G-AN 5G Access Network    -   5QI 5G QoS Indicator    -   AF Application Function    -   AMF Access and Mobility Management Function    -   AN Access Network    -   ARP Allocation and Retention Priority    -   CDR Charging Data Record    -   CCNF Common Control Network Functions    -   CN Core Network    -   CP Control Plane    -   DL Downlink    -   DN Data Network    -   DN-AAA Data Network Authentication Authorization and Accounting    -   DNN Data Network Name    -   ESP Encapsulating Security Payload    -   gNB NR NodeB    -   IETF Internet Engineering Task Force    -   IP Internet Protocol    -   L2 Layer 2 (data link layer)    -   L3 Layer 3 (network layer)    -   LADN Local Area Data Network    -   LI Lawful Intercept    -   MICO Mobile Initiated Connection Only    -   MME Mobility Management Entity    -   N3IWF Non-3GPP InterWorking Function    -   NAI Network Access Identifier    -   NAS Non Access Stratum    -   NEF Network Exposure Function    -   NF Network Function    -   NG-RAN NR Radio Access Network    -   NR New Radio    -   NRF Network Repository Function    -   NSI Network Slice Instance    -   NSSAI Network Slice Selection Assistance Information    -   NSSF Network Slice Selection Function    -   OCS Online Charging System    -   OFCS Offline Charging System    -   PCC Policy and Charging Control    -   PCF Policy Control Function    -   PDU Packet Data Unit    -   PDCP Packet Data Convergence Protocol    -   RB Radio Bearer    -   RFC Request For Comments    -   RLC Radio Link Control    -   ROHC Robust Header Compression    -   RRC Radio Resource Control    -   PEI Permanent Equipment Identifier    -   PLMN Public Land Mobile Network    -   RAN Radio Access Network    -   QFI QoS Flow Identity    -   RM Registration Management    -   SBA Service Based Architecture    -   SCM Security Context Management    -   SDAP Service Data Adaptation Protocol    -   SDU Service Data Unit    -   SEA Security Anchor Function    -   SMF Session Management Function    -   SMSF SMS Function    -   SN Sequence Number    -   S-NSSAI Single Network Slice Selection Assistance information    -   SRB Signaling Radio Bearer carrying control plane data    -   SUPI Subscriber Permanent Identifier    -   TA Tracking Area    -   TAI Tracking Area Identity    -   TCP Transmission Control Protocol    -   UDM Unified Data Management    -   UDP User Datagram Protocol    -   UE User Equipment    -   UL Uplink    -   UL CL Uplink Classifier    -   UPF User Plane Function

Example FIG. 1 and FIG. 2 depict a 5G system comprising of accessnetworks and 5G core network. An example 5G access network may comprisean access network connecting to a 5G core network. An access network maycomprise a NG-RAN 105 and/or non-3GPP AN 165. An example 5G core networkmay connect to one or more 5G access networks 5G-AN and/or NG-RANs. 5Gcore network may comprise functional elements or network functions as inexample FIG. 1 and example FIG. 2 where interfaces are employed forcommunication among the functional elements and/or network elements.

A network function may be a processing function in a network, which hasa functional behavior and interfaces. A network function may beimplemented either as a network element on a dedicated hardware, and/ora network node as depicted in FIG. 3 and FIG. 4 , or as a softwareinstance running on a dedicated hardware and/or shared hardware, or as avirtualized function instantiated on an appropriate platform.

Access and mobility management function, AMF 155, may include thefollowing functionalities (some of the AMF functionalities may besupported in a single instance of an AMF 155): termination of RAN CPinterface (N2), termination of NAS (N1), NAS ciphering and integrityprotection, registration management, connection management, reachabilitymanagement, mobility management, lawful intercept (for AMF 155 eventsand interface to LI system), provide transport for session management,SM messages between UE 100 and SMF 160, transparent proxy for routing SMmessages, access authentication, access authorization, provide transportfor SMS messages between UE 100 and SMSF, security anchor function, SEA,interaction with the AUSF 150 and the UE 100, receiving the intermediatekey established as a result of the UE 100 authentication process,security context management, SCM, that receives a key from the SEA thatit uses to derive access network specific keys.

The AMF 100 may support non-3GPP access networks through N2 interfacewith N3IWF 170, NAS signaling with a UE 100 over N3IWF 170,authentication of UEs connected over N3IWF 170, management of mobility,authentication, and separate security context state(s) of a UE 100connected via non-3GPP access 165 or connected via 3GPP and non-3GPPaccesses 105, 165 simultaneously, support of a coordinated RM contextvalid over 3GPP and non 3GPP accesses 105, 165, support of CM managementcontexts for the UE 100 for connectivity over non-3GPP access. Some offunctionalities described above may be supported in an instance of anetwork slice.

In an example, an AMF 155 region may comprise of one or multiple AMF 100sets. AMF 155 set comprises of some AMFs 155 that serve a given areaand/or network slice(s). In an example, multiple AMF 155 sets may be perAMF 155 region and/or network slice(s). Application identifier may be anidentifier that may be mapped to a specific application trafficdetection rule. Configured NSSAI may be an NSSAI that has beenprovisioned in a UE 100. DN 115 access identifier (DNAI), for a DNN, maybe an identifier of a user plane access to a DN 115. Initialregistration may be related to a UE 100 registration in RM-DEREGISTERED500, 520 state. N2AP UE 100 association may be a logical per UE 100association between a AN node and an AMF 155. N2AP UE-TNLA-binding maybe a binding between a N2AP UE 100 association and a specific transportnetwork layer, TNL association for a given UE 100.

The session management function, SMF 160, may include one or more of thefollowing functionalities (one or more of the SMF 160 functionalitiesmay be supported in a single instance of a SMF 160): session management(e.g. session establishment, modify and release, including tunnelmaintain between UPF 110 and AN 105 node), UE 100 IP address allocation& management (including optional authorization), selection and controlof UP function(s), configuration of traffic steering at UPF 110 to routetraffic to proper destination, termination of interfaces towards policycontrol functions, control part of policy enforcement and QoS. lawfulintercept (for SM events and interface to LI System), termination of SMparts of NAS messages, downlink data notification, initiation of ANspecific SM information, sent via AMF 155 over N2 to (R)AN 105,determination of SSC mode of a session, roaming functionality, handlinglocal enforcement to apply QoS SLAs (VPLMN), charging data collectionand charging interface (VPLMN), lawful intercept (in VPLMN for SM eventsand interface to LI System), support for interaction with external DN115 for transport of signaling for PDU sessionauthorization/authentication by external DN 115. One or more offunctionalities described above may be required to be supported in aninstance of a network slice.

The user plane function, UPF 110, may include one or more of thefollowing functionalities (some of the UPF 110 functionalities may besupported in a single instance of a UPF 110): anchor point forIntra-/Inter-RAT mobility (when applicable), external PDU session pointof interconnect to DN 115, packet routing & forwarding, packetinspection and user plane part of policy rule enforcement, lawfulintercept (UP collection), traffic usage reporting, uplink classifier tosupport routing traffic flows to a data network, branching point tosupport multi-homed PDU session(s), QoS handling for user plane, uplinktraffic verification (SDF to QoS flow mapping), transport level packetmarking in the uplink and downlink, downlink packet buffering anddownlink data notification triggering. One or more of functionalitiesdescribed above may be supported in an instance of a network slice.

The UE 100 IP address management may include allocation and release ofthe UE 100 IP address as well as renewal of the allocated IP address,where applicable. The UE 100 sets the requested PDU type during the PDUsession establishment procedure based on its IP stack capabilities andconfiguration. In an example, the SMF 160 may select PDU type of a PDUsession as follows: If the SMF 160 receives a request with PDU type setto IP, the SMF 160 may select either PDU type IPv4 or IPv6 based on DNNconfiguration and operator policies. A SMF 160 may provide a cause valueto the UE 100 to indicate whether the other IP version is supported onthe DNN. If the other IP version is supported, UE 100 may requestanother PDU Session to the same DNN for the other IP version. If the SMF160 receives a request for PDU type IPv4 or IPv6 and the requested IPversion is supported by the DNN the SMF selects the requested PDU type.

In an example embodiment, the 5GC elements and UE 100 support thefollowing mechanisms: during PDU session establishment procedure, theSMF 160 may send the IP address to the UE 100 via SM NAS signaling. TheIPv4 address allocation and/or IPv4 parameter configuration via DHCPv4may be employed once PDU session is established. IPv6 prefix allocationmay be supported via IPv6 stateless autoconfiguration, if IPv6 issupported. IPv6 parameter configuration via stateless DHCPv6 may besupported.

The 5GC may support the allocation of a static IPv4 address and/or astatic IPv6 prefix based on subscription information in the UDM 140 orbased on the configuration on a per-subscriber, per-DNN basis.

User plane function(s) (UPF(s) 110) may handle the user plane path ofPDU sessions. A UPF 110 that provides the interface to a data networksupports the functionality of a PDU session anchor.

The policy control function, PCF 135, may support unified policyframework to govern network behavior, provide policy rules to controlplane function(s) to enforce them, implement a front end to accesssubscription information relevant for policy decisions in a user datarepository (UDR).

The network exposure function, NEF 125, may provide a means to securelyexpose the services and capabilities provided by the 3GPP networkfunctions, translate between information exchanged with the AF 145 andinformation exchanged with the internal network functions, receiveinformation from other network functions.

The NF repository function, NRF 130 may support service discoveryfunction that receives NF discovery request from NF instance, providethe information of the discovered NF instances (be discovered) to the NFinstance, and maintain the information of available NF instances andtheir supported services.

The unified data management, UDM 140, may comprise of the applicationfront end (FE) that includes the UDM-FE that is in charge of processingcredentials, location management, subscription management and the PCF135 in charge of policy control; and the user data repository, UDR, thatstores data required for functionalities provided by UDM-FE, plus policyprofiles required by the PCF 135.

The NSSF may support selecting the set of network slice instancesserving the UE 100, determining the Allowed NSSAI, determining the AMF155 set to be employed to serve the UE 100, and/or, based onconfiguration, determining a list of candidate AMF(s) 155, possibly byquerying the NRF 130.

The data stored in the UDR include at least user subscription data,including at least subscription identifiers, security credentials,access and mobility related subscription data and/or session relatedsubscription data and/or policy data.

The AUSF 150 may support authentication server function (AUSF). Thefunctionality of N3IWF 170 in case of untrusted non-3GPP access 165 mayinclude at least one or more of the following: support of IPsec tunnelestablishment with the UE; The N3IWF 170 may terminate the IKEv2/IPsecprotocols with the UE 100 over NWu and may relay over N2 the informationneeded to authenticate the UE 100 and authorize its access to the 5Gcore network; Termination of N2 and N3interfaces to 5G Core Network forControl-Plane and user-plane respectively; Relaying uplink and downlinkcontrol-plane NAS (N1) signaling between the UE 100 and AMF 155;Handling of N2 signaling from SMF 160 (relayed by AMF 155) related toPDU sessions and QoS; Establishment of IPsec Security Association (IPsecSA) to support PDU session traffic; Relaying uplink and downlinkuser-plane packets between the UE 100 and UPF 110; Enforcing QoScorresponding to N3packet marking, considering QoS requirementsassociated to such marking received over N2; N3user-plane packet markingin the uplink; and/or local mobility anchor within untrusted non-3GPPaccess networks 165 using MOBIKE; Supporting AMF 155 selection.

The application function, AF 145, may interact with the 3GPP corenetwork to provide services. Based on operator deployment, applicationfunctions may be trusted by the operator to interact directly withrelevant network functions. Application functions not allowed by theoperator to access directly the network functions may use the externalexposure framework (via the NEF 125) to interact with relevant networkfunctions.

The control plane interface between the (R)AN 105 and the 5G core maysupport connection of multiple different kinds of AN(s) (e.g. 3GPP RAN105, N3IWF 170 for Un-trusted access 165) to the 5GC via a uniquecontrol plane protocol. A single N2 AP protocol may be employed for boththe 3GPP access 105 and non-3GPP access 165; and decoupling between AMF155 and other functions such as SMF 160 that may need to control theservices supported by AN(s) (e.g. control of the UP resources in the AN105 for a PDU session).

The 5GC may be able to provide policy information from the PCF 135 tothe UE 100. Such policy information may include but not limited to thefollowing: access network discovery & selection policy, UE 100 routeselection policy (URSP) that groups to or more of SSC mode selectionpolicy (SSCMSP), network slice selection policy (NSSP), DNN selectionpolicy, and non-seamless offload policy.

The 5G core network may support the connectivity of a UE 100 vianon-3GPP access networks 165. As shown in example FIG. 5 , theregistration management, RM may be employed to register or de-register aUE/user 100 with the network, and establish the user context in thenetwork. Connection management may be employed to establish and releasethe signaling connection between the UE 100 and the AMF 155.

A UE 100 may need to register with the network to receive services thatrequire registration. Once registered and if applicable the UE 100 mayupdate its registration with the network periodically in order to remainreachable (periodic registration update); or upon mobility (mobilityregistration update); or to update its capabilities or re-negotiateprotocol parameters.

The initial registration procedure as depicted in example FIG. 8 andFIG. 9 may involve execution of network access control functions (e.g.user authentication and access authorization based on subscriptionprofiles in UDM 140). As result of the registration procedure, theidentity of the serving AMF 155 may be registered in UDM 140.

The registration management, RM procedures may be applicable over both3GPP access 105 and non 3GPP access 165.

An example FIG. 5 depicts the RM states of a UE 100 as observed by theUE 100 and AMF 155. In an example embodiment, two RM states may beemployed in a UE 100 and the AMF 155 that reflect the registrationstatus of the UE 100 in the selected PLMN: RM-DEREGISTERED 500, andRM-REGISTERED 510. In the RM DEREGISTERED state 500, the UE 100 may notbe registered with the network. The UE 100 context in AMF 155 may nothold valid location or routing information for the UE 100 so the UE 100is not reachable by the AMF 155. Some UE 100 context may still be storedin the UE 100 and the AMF 155. In the RM REGISTERED state 510, the UE100 may be registered with the network. In the RM-REGISTERED 510 state,the UE 100 may receive services that require registration with thenetwork.

In an example embodiment, two RM states may be employed in AMF 155 for aUE 100 that reflect the registration status of the UE 100 in theselected PLMN: RM-DEREGISTERED 520, and RM-REGISTERED 530.

As shown in example FIG. 6 , connection management, CM, may comprise thefunctions of establishing and releasing a signaling connection between aUE 100 and the AMF 155 over N1. This signaling connection may beemployed to enable NAS signaling exchange between the UE 100 and a corenetwork. It comprises both the AN signaling connection between the UE100 and the (R)AN 105 (e.g. RRC connection over 3GPP access) and the N2connection for this UE 100 between the AN and the AMF 155.

As depicted in example FIG. 6 , two CM states may be employed for theNAS signaling connectivity of the UE 100 with the AMF 155, CM-IDLE 600,620 and CM-CONNECTED 610, 630. A UE 100 in CM-IDLE 600 state is inRM-REGISTERED 510 state and has no NAS signaling connection establishedwith the AMF 155 over Ni. The UE 100 may perform cell selection, cellreselection and PLMN selection. A UE 100 in CM-CONNECTED 610 state has aNAS signaling connection with the AMF 155 over N1.

In an example embodiment two CM states may be employed for a UE 100 atthe AMF 155, CM-IDLE 620 and CM-CONNECTED 630.

RRC inactive state may apply to NG-RAN (e.g. it applies to NR and E-UTRAconnected to 5G CN). The AMF 155, based on network configuration, mayprovide assistance information to the NG RAN 105, to assist the NG RAN's105 decision whether the UE 100 is sent to RRC inactive state. When a UE100 is CM-CONNECTED 610 with RRC inactive state, the UE 100 may resumethe RRC connection due to uplink data pending; Mobile initiatedsignaling procedure; As a response to RAN 105 paging; Notifying thenetwork that it has left the RAN 105 notification area.

NAS signaling connection management may include the functions ofestablishing and releasing a NAS signaling connection. NAS signalingconnection establishment function may be provided by the UE 100 and theAMF 155 to establish a NAS signaling connection for a UE 100 in CM-IDLE600 state. The procedure of releasing a NAS signaling connection may beinitiated by the 5G (R)AN 105 node or the AMF 155.

Reachability management of UE 100 may detect whether a UE 100 isreachable and providing UE 100 location (e.g. access node) for thenetwork to reach the UE 100. This may be done by paging UE 100 and UE100 location tracking. The UE 100 location tracking may include both UE100 registration area tracking and UE 100 reachability tracking. Suchfunctionalities may be either located at 5GC (in case of CM-IDLE 620state) or NG-RAN 105 (in case of CM-CONNECTED 630 state). The UE 100 andthe AMF 155 may negotiate UE 100 reachability characteristics in CM-IDLE600, 620 state during registration and registration update procedures.

Two UE 100 reachability categories may be negotiated between a UE 100and an AMF 155 for CM-IDLE 600, 620 state. 1) UE 100 reachabilityallowing mobile device terminated data while the UE 100 is CM-IDLE 600mode. 2) Mobile initiated connection only (MICO) mode. The 5GC maysupport a PDU connectivity service that provides exchange of PDUsbetween a UE 100 and a data network identified by a DNN. The PDUconnectivity service may be supported via PDU sessions that areestablished upon request from the UE 100.

A PDU session may support one or more PDU session types. PDU sessionsmay be established (e.g. upon UE 100 request), modified (e.g. upon UE100 and 5GC request) and released (e.g. upon UE 100 and 5GC request)using NAS SM signaling exchanged over N1 between the UE 100 and the SMF160. Upon request from an application server, the 5GC may be able totrigger a specific application in the UE 100. When receiving thattrigger message, the UE 100 may pass it to the identified application inthe UE 100. The identified application in the UE 100 may establish a PDUsession to a specific DNN.

The 5G QoS model may support a QoS flow based framework as shown inexample FIG. 7 . The 5G QoS model may support both QoS flows thatrequire a guaranteed flow bit rate and QoS flows that may not require aguaranteed flow bit rate. The 5G QoS model may support reflective QoS.The QoS model may comprise flow mapping or packet marking at the UPF(CN_UP) 110, AN 105 and/or UE 100. Packets may arrive from and/ordestined to the application/service layer 730 of UE 100, UPF (CN_UP)110, and/or the AF 145.

QoS flow may be a granularity of QoS differentiation in a PDU session. AQoS Flow ID, QFI, may be employed to identify a QoS flow in the 5Gsystem. User plane traffic with the same QFI within a PDU session mayreceive the same traffic forwarding treatment. The QFI may be carried inan encapsulation header on N3(and N9) e.g. without any changes to theend-to-end packet header. It may be applied to PDUs with different typesof payload. The QFI may be unique within a PDU session.

The QoS parameters of a QoS flow may be provided to the (R)AN as a QoSprofile over N2 at PDU session or at QoS flow establishment and whenNG-RAN is used at every time the user plane is activated. A default QoSrule may be required for every PDU session. The SMF 160 may allocate theQFI for a QoS flow and may derive its QoS parameters from theinformation provided by the PCF. When applicable, the SMF 160 mayprovide the QFI together with the QoS profile containing the QoSparameters of a QoS flow to the (R)AN 105.

5G QoS flow may be a granularity for QoS forwarding treatment in a 5Gsystem. Traffic mapped to the same 5G QoS flow may receive the sameforwarding treatment (e.g. scheduling policy, queue management policy,rate shaping policy, RLC configuration, and/or the like). Providingdifferent QoS forwarding treatment may require separate 5G QoS flow.

A 5G QoS indicator may be a scalar that is employed as a reference to aspecific QoS forwarding behavior (e.g. packet loss rate, packet delaybudget) to be provided to a 5G QoS flow. This may be implemented in theaccess network by the 5QI referencing node specific parameters thatcontrol the QoS forwarding treatment (e.g. scheduling weights, admissionthresholds, queue management thresholds, link layer protocolconfiguration, and/or the like.).

5GC may support edge computing and may enable operator(s) and 3rd partyservices to be hosted close to the UE's access point of attachment. The5G core network may select a UPF 110 close to the UE 100 and may executethe traffic steering from the UPF 110 to the local data network via a N6interface. This may be based on the UE's 100 subscription data, UE 100location, the information from application function AF 145, policy orother related traffic rules. The 5G core network may expose networkinformation and capabilities to an edge computing application function.The functionality support for edge computing may include local routingwhere the 5G core network may select UPF 110 to route the user trafficto the local data network, traffic steering where the 5G core networkselects the traffic to be routed to the applications in the local datanetwork, session and service continuity to enable UE 100 and applicationmobility, user plane selection and reselection, e.g. based on input fromapplication function, network capability exposure where 5G core networkand application function may provide information to each other via NEF,QoS and charging where PCF may provide rules for QoS control andcharging for the traffic routed to the local data network, support oflocal area data network where 5G core network may provide support toconnect to the LADN in a certain area where the applications aredeployed.

An example 5G system may be a 3GPP system comprising of 5G accessnetwork 105, 5G core network and a UE 100, and/or the like. AllowedNSSAI may be an NSSAI provided by a serving PLMN during e.g. aregistration procedure, indicating the NSSAI allowed by the network forthe UE 100 in the serving PLMN for the current registration area.

PDU connectivity service may provide exchange of PDUs between a UE 100and a data network. PDU session may be an association between a UE 100and a data network, DN, that provides a PDU connectivity service. Thetype of association may be IP, or Ethernet or unstructured.

Establishment of user plane connectivity to a data network via a networkslice instance(s) comprises of at least two steps. Performing a RMprocedure to select an AMF 155 that supports the required networkslices, and establishing one or more PDU session(s) to the required datanetwork via the network slice instance(s).

The set of network slices for a UE 100 may be changed at any time whilethe UE 100 is registered with a network, and may be initiated by thenetwork, or the UE 100.

A periodic registration update may be UE 100 re-registration at expiryof a periodic registration timer. A requested NSSAI is a NSSAI that theUE 100 may provide to the network. A service based interface mayrepresent how a set of services is provided/exposed by a given NF.

A service continuity may be an uninterrupted user experience of aservice, including the cases where the IP address and/or anchoring pointchange. A session continuity may refer to continuity of a PDU session.For PDU session of IP type session continuity may imply that the IPaddress is preserved for the lifetime of the PDU session. An uplinkclassifier may be a UPF functionality that aims at diverting uplinktraffic, based on filter rules provided by SMF, towards data network.

The 5G system architecture may support data connectivity and servicesenabling deployments to use techniques such as e.g. network functionvirtualization and/or software defined networking. The 5G systemarchitecture may leverage service-based interactions between controlplane (CP) network functions where identified. In 5G systemarchitecture, separation of the user plane (UP) functions from thecontrol plane functions may be considered. A 5G system may enable anetwork function to interact with other NF(s) directly if required.

A 5G system may reduce dependencies between the access network (AN) andthe core network (CN). The architecture may comprise a convergedaccess-agnostic core network with a common AN-CN interface whichintegrates different 3GPP and non-3GPP access types.

A 5G system furthermore may support a unified authentication framework,stateless NFs, where the compute resource is decoupled from the storageresource, capability exposure, and concurrent access to local andcentralized services. To support low latency services and access tolocal data networks, UP functions may be deployed close to the accessnetwork.

A 5G system may support roaming with both home routed traffic as well aslocal breakout traffic in the visited PLMN. An example 5G architecturemay be service-based and the interaction between network functions maybe represented in two ways. (1) FIG. 1 is an example service-basedrepresentation, where network functions within the control plane, mayenable other authorized network functions to access their services. Thisrepresentation may include point-to-point reference points wherenecessary. (2) FIG. 2 is an example reference point representation,showing the interaction between the NF services in the network functionsdescribed by point-to-point reference point (e.g. N11) between any twonetwork functions.

FIG. 10 is an example diagram of control plane interfaces for networkslicing as per an aspect of an embodiment of the present invention. FIG.10 shows control plane network functions (CP NFs) and user plane networkfunctions (UP NFs) for example slice A, slice B, and slice C.

One or more RAN or core network nodes may use a slice routing andselection function (SSF) 120 to link radio access bearer(s) of a UE withthe corresponding core network instance(s). The Subscriber Repository140 may contain subscriber profiles which may be used for authorization.The Subscriber Repository 140 may also include user identities andcorresponding long-term credentials for authentication. The RAN 105 mayappear as one RAT+PLMN to a UE and an association with network instancemay be performed by network internally. In an example implementation,the network slices may not be visible to the UE. Common CP NFs 901 maybe the CP entry function, which may include the mobility managementfunction, authentication function, and NAS proxy function. The common CPmay be shared parts among different slices. When different types ofnetwork slice do the sharing, the required common CP function may bedifferent.

FIG. 11 is an example diagram depicting UE1 100-1, UE2 100-2, and UE3100-3 that are assigned to a core part of network slice instances (NSI)as per an aspect of an embodiment of the present invention. UE1 100-1,UE2 100-2 and UE3 100-3 may be connected to specific core networkfunctions via RAN 105. The core network part of the network slice mayshare some network functions with other core network part of networkslices which serve the same UE, including the NG1 and NG2 terminations,in the common control network functions (CCNF). As an example, in theFIG. 11 , UE1 100-1 and UE3 100-3 may be assigned to Common CP NF 1901-1, and may have 3 slices accessing multiple core network sliceinstances (NSIs) and therefore multiple slice-specific core networkfunctions. UE2 100-2 may be associated with 1 NSI and is assigned todifferent Common CP NF 2 901-2 after the UEs attach to has occurred.

FIG. 12 is an example diagram depicting network slice architecture withtwo groups-common CP NFs and dedicated CP NFs as per an aspect of anembodiment of the present invention. In an example, the core NetworkInstances may be set up to enable a UE to simultaneously obtain servicesfrom multiple network slices of one network operator. A single set ofC-Plane Functions that are in common among core network instances may beshared across multiple core network instances. In an example, U-planefunctions and other C-Plane functions that are not in common may residein their respective core network instances, and may be not shared withother core network instances.

In an example embodiment, a slice instance ID may be an identifier of anetwork slice instance. A slice instance ID may be used as an indicatorby the network to select the corresponding slice for a UE. A CP-NF IDmay be an identifier of a control plane network function instance. In anexample, the NSSF (Network Slice Selection Function) 120 may be commonto network slices in the PLMN and may realize the slice selectionfunction for both groups.

The NSSF 120 may store the mapping information between slice instance IDand NF ID (or NF address). The NSSF 120 may have connection with thesubscriber repository 140 to get the UE's subscribed slice instance IDscorresponding to current PLMN. NSSF 120 may obtain network sliceselection policy from policy function. CP-NF ID or address may bedetermined by the NSSF 120 based on slice instance ID, UE's subscribedinformation, and/or network slice selection policy. NSSF 120 may respondthe specific CP-NF ID/address corresponding to the slice instance ID tothe RAN 105. The NSSF 120 may be located in the core network, which maybe useful for the interaction and mapping update between the NSSF 120and subscriber repository 140, and this may make the management of themapping between Slice Instance ID and NF ID/address in a centralizedway. The RAN 105 may act as a routing function to link the UE with theappropriate CN part of network slice. The RAN 105 may store the mappingbetween the Slice Instance ID and NF ID. The Common CP NFs 901 may beused for multiple slices with UE simultaneously connected. A UE mayaccess multiple network slices at the same time, the Common CP NFs 901may have common set of NFs which may be flexibly expanded withadditional NFs per slice requirement.

In an example, when a UE is slice-enabled, there may be one or morecases for the attach procedure. According to an example embodiment, a UEmay attach without Slice Instance ID. The UE may or may not take someassistant parameters (e.g. service type). The RAN 105 may forward theattach request to NSSF 120. NSSF 120, may check with subscription dataand network slice selection policy, response with a predefined/defaultSlice Instance ID to the UE. According to an example embodiment, a UEmay attach with a Slice Instance ID. In an example, the RAN 105 may notknow the corresponding slice. The RAN 105 may forward the UE requestsignaling to NSSF 120 and NSSF 120 may respond with specific CP-NFID/address corresponding to the Slice Instance ID. The RAN 105 may routethe attach request to the specific CP-NF. According to an exampleembodiment, a UE may attach with a Slice Instance ID. The RAN 105 mayhave the related mapping between the Slice Instance ID carried by UE andCP-NF ID. The attach request may be routed to the specific CP-NF in thecore network.

FIG. 13 is an example diagram depicting multiple slices per UE as per anaspect of an embodiment of the present invention. The network sliceinstances may be independent and they may not share any CP or UPfunctions. They may share common databases such as the subscriptiondatabase and/or policy databases. Network slices instances maycommunicate via the NGs interface. Each network slice instance may havea unique slice identity that may be resolved to an IP address forcommunication via NGs. A UE 100 may be simultaneously attached tomultiple network slice instances. One of these slices may be the primarynetwork slice 1201 for the UE 100 and all the others may be secondarynetwork slices 1202 for the UE 100. The first attach performed by the UE100 may be called initial attach and attaches the UE 100 to the primarynetwork slice 1201, and a subsequent attach may be called additionalattach and attaches the UE 100 to a secondary network slice 1202.

A Network Slice may include at least one of the following: the CoreNetwork Control Plane and user plane Network Functions; the 5G RadioAccess Network; and/or the N3IWF functions to the non-3GPP AccessNetwork. Network slices may differ for supported features and networkfunctions implementation. The operator may deploy multiple Network Sliceinstances delivering the same features but for different groups of UEs,e.g. as they deliver a different committed service and/or because theymay be dedicated to a customer. The NSSF may store the mappinginformation between slice instance ID and NF ID (or NF address).

A single UE may simultaneously be served by one or more network sliceinstances via a 5G-AN. In an example, a single UE may be served by knetwork slices (e.g. k=8, 16, etc.) at a time. An AMF instance servingthe UE logically belongs to a Network Slice instances serving the UE.

In an example, a PDU session may belong to one specific network sliceinstance per PLMN. In an example, different network slice instances maynot share a PDU session. Different slices may have slice-specific PDUsessions using the same DNN.

An S-NSSAI (Single Network Slice Selection Assistance information) mayidentify a Network Slice. An S-NSSAI may be comprised of: aslice/service type (SST), which may refer to the expected Network Slicebehavior in terms of features and services; and/or a slicedifferentiator (SD). A slice differentiator may be optional informationthat complements the slice/service type(s) to allow furtherdifferentiation for selecting an network slice instance from potentiallymultiple network slice instances that comply with the indicatedslice/service type. This information may be referred to as SD. The sameNetwork Slice instance may be selected employing different S-NSSAIs. TheCN part of a Network Slice instance(s) serving a UE may be selected byCN.

Subscription data may include the S-NSSAI(s) of the Network Slices thatthe UE subscribes to. One or more S-NSSAIs may be marked as defaultS-NSSAI. In an example, k S-NSSAI may be marked Default S-NSSAI (e.g.k=8, 16, etc.). In an example, the UE may subscribe to more than 8S-NSSAI.

A UE may be configured by the HPLMN with a Configured NSSAI per PLMN.Upon successful completion of a UE's Registration procedure, the UE mayobtain from the AMF an Allowed NSSAI for this PLMN, which may includeone or more S-NSSAIs.

The Allowed NSSAI may take precedence over the Configured NSSAI for thisPLMN. The UE may use the S-NSSAIs in the Allowed NSSAI corresponding toa Network Slice for the subsequent Network Slice selection relatedprocedures in the serving PLMN.

The establishment of user plane connectivity to a data network via anetwork slice instance(s) may comprise one or more of the followingsteps: performing a RM procedure to select an AMF that supports therequired Network Slices; establishing one or more PDU session to therequired Data network via the Network Slice Instance(s).

When a UE registers with a PLMN, if the UE for this PLMN has aconfigured NSSAI or an allowed NSSAI, the UE may provide to the networkin RRC and NAS layer a Requested NSSAI containing the S-NSSAI(s)corresponding to the slice(s) to which the UE attempts to register, inaddition to the temporary user ID if one was assigned to the UE. TheRequested NSSAI may be either: the Configured-NSSAI; the Allowed-NSSAI.

In an example, when a UE registers with a PLMN, if for this PLMN the UEhas no Configured NSSAI or Allowed NSSAI, the RAN may route NASsignaling from/to this UE to/from a default AMF.

The network, based on local policies, subscription changes and/or UEmobility, may change the set of permitted Network Slice(s) to which theUE is registered. The network may perform such change during aRegistration procedure or trigger a notification towards the UE of thechange of the supported Network Slices using an RM procedure (which maytrigger a Registration procedure). The Network may provide the UE with anew Allowed NSSAI and Tracking Area list.

During a Registration procedure in a PLMN, in case the network decidesthat the UE should be served by a different AMF based on NetworkSlice(s) aspects, then the AMF that first received the RegistrationRequest may redirect the Registration request to another AMF via the RANor via direct signaling between the initial AMF and the target AMF. Thenetwork operator may provision the UE with Network Slice selectionpolicy (NSSP). The NSSP includes one or more NSSP rules. An NSSP rulemay associate an application with a certain S-NSSAI. A default rulewhich matches one or more applications to a S-NSSAI may also beincluded. When a UE application associated with a specific S-NSSAIrequests data transmission, then: if the UE has one or more PDU sessionsestablished corresponding to the specific S-NSSAI, the UE may route theuser data of this application in one of these PDU sessions, unless otherconditions in the UE prohibit the use of these PDU sessions. If theapplication provides a DNN, then the UE may consider also this DNN todetermine which PDU session to use. When a UE application associatedwith a specific S-NSSAI requests data transmission, then if the UE doesnot have a PDU session established with this specific S-NSSAI, the UEmay request a new PDU session corresponding to this S-NSSAI and with theDNN that may be provided by the application. In order for the RAN toselect a proper resource for supporting network slicing in the RAN, RANmay be aware of the Network Slices used by the UE.

The AMF may select an SMF in a Network Slice instance based on S-NSSAI,DNN and other information e.g. UE subscription and local operatorpolicies, when the UE triggers the establishment of a PDU session. Theselected SMF may establish a PDU session based on S-NSSAI and DNN.

In an example, in order to support network-controlled privacy of sliceinformation for the slices the UE accesses, when the UE is aware orconfigured that privacy considerations apply to NSSAI: The UE may notinclude NSSAI in NAS signaling unless the UE has a NAS security contextand the UE may not include NSSAI in unprotected RRC signaling.

For roaming scenarios, the Network Slice specific network functions inVPLMN and HPLMN may be selected based on the S-NSSAI provided by the UEduring PDU connection establishment. If a standardized S-NSSAI is used,then selections of slice specific NF instances may be done by each PLMNbased on the provided S-NSSAI. Otherwise, the VPLMN may map the S-NSSAIof HPLMN to a S-NSSAI of VPLMN based on roaming agreement (includingmapping to a default S-NSSAI of VPLMN). The selection of slice specificNF instance in VPLMN may be done based on the S-NSSAI of VPLMN. Theselection of any slice specific NF instance in HPLMN may be based on theS-NSSAI of HPLMN.

Implementation of the existing technologies for a network slice may haveissues in supporting an isolated network slice, e.g. current solutionsdo not specify how to implement an isolated network slice, how to selecta proper AMF for an isolated network slice. Implementation of theexisting technologies for a network slice may have issues in supportingdifferent kind/level of isolated network slice without selecting aproper AMF. Example embodiments provides enhanced mechanisms toimplement an isolated network slice. Example embodiments providesenhanced mechanisms to select a proper AMF for different kind/level ofan isolated network slice.

Example 1

In an example, the UE may request fully isolated network slice(s) whenperforming the registration procedure, an NRF may select an AMF for thefully isolated network slice(s). There are example different kind/levelof isolated network slices. In an example, a fully isolated networkslice may be a kind/level of isolated network slice. For a fullyisolated network slice, a network slice instance may not share neitherthe (R)AN nor the core network (e.g. comprising the control plane anduser plane) network function with any other network slice instance. Asan example, network slice instance 1 and network slice instance 2 inFIG. 18 are two fully isolated network slices, no network functions areshared by these two network slice instances. In an example, a partlyisolated network slice with (R)AN shared may be a kind/level of isolatednetwork slice. For a partly isolated network slice with (R)AN shared,(R)AN belonging to an isolated network slice instance may be the NF thatcan be seen from the outside of the network slice instance (e.g. fromthe PLMN level NRF). FIG. 19 shows an example, where network sliceinstance 1 and network slice instance 2 are two partly isolated networkslices, (R)AN 105 may be shared by the network slice instance 1 andnetwork slice instance 2. In an example, a partly isolated network slicewith (R)AN and AMF shared may be a kind/level of isolated network slice.For a partly isolated network slice with (R)AN and AMF shared, both(R)AN and AMF(s) belonging to an isolated network slice instance are NFsthat can be seen from the outside of the network slice instance. FIG. 20shows an example, where network slice instance 1 and network sliceinstance 2 are two partly isolated network slices, (R)AN 105 and AMF 155may be shared by the network slice instance 1 and network slice instance2.

FIG. 14 is an example call flow diagram as per an aspect of anembodiment of the present disclosure. UE 100 may send a registrationrequest to a (R)AN 105 comprising an AN message. The AN message maycomprise AN parameters and/or a RM-NAS Registration Request, wherein theRM-NAS Registration Request may comprise at least one of: a registrationtype, UE identifier(s) (e.g. SUPI and/or 5G-GUTI), security parameters,a requested NSSAI, DNN, A UE SGCN Capability, a PDU session status, PDUsession(s) to be re-activated, a follow on request, or a MICO modepreference. The Requested NSSAI may comprise one or more S-NSSAIscorresponding to one or more network slices or network slice instancesto which the UE may register. The DNN is the data network name, whichmay be equivalent to an APN the UE may access. The PDU session statusand/or PDU session(s) to be re-activated may comprise the PDU sessionID(s). The UE 100 may comprise network slice isolation information inthe registration request, and the network slice isolation informationmay comprise one of the following network slice isolation type/level foreach of the requested S-NSSAI and/or the requested S-NSSAI relatednetwork slice instance: Fully isolated network slice; Partly isolatednetwork slice with (R)AN shared; or Partly isolated network slice with(R)AN and AMF shared. As an example, the network slice isolationinformation may be comprised in S-NSSAI as illustrated in example FIG.21 . As an example, the network slice isolation information may becomprised in a new information element as illustrated in example FIG. 22.

In an example, a fully isolated network slice value may be set by the UE100 for the network slice isolation type (NSIT). As an example, thenetwork slice isolation information may comprise a parameter to indicatethe network slice is logically isolated or physically isolated from theone or more other network slices.

In response to the message received from the UE 100, the (R)AN 105, maysend to an NRF 130 a message (e.g. Nnrf NFDiscovery Request) to selectan AMF, and the message may comprise one or more of the followinginformation received from the UE 100: Requested NSSAI; Requested networkslice isolation information (e.g. network slice isolation type/levelapplied to the requested NSSAI and/or the requested NSSAI relatednetwork slice instance(s)); UE identifier(s) (e.g. SUPI and/or 5G-GUTI);PDU session ID(s); and DNN.

In response to the message received from the (R)AN 105, the NRF 130 maysend the UDM 140 a message (e.g. subscriber data request) to request thesubscription information of the UE 100, the message may comprise one ormore of the following information: Requested NSSAI; Requested networkslice isolation information (e.g. network slice isolation type/levelapplied to the requested NSSAI and/or the requested NSSAI relatednetwork slice instance(s)); UE identifier(s) (e.g. SUPI and/or 5G-GUTI);PDU session ID(s); and DNN.

In response to the message received from the NRF 130, the UDM 140 maysend to the NRF 130 a response message (e.g. subscriber data response),and the message may comprise one or more of the following information:Subscribed NSSAI and/or subscribed NSSAI related network sliceinstance(s), where the subscribed NSSAI may comprise one or moreS-NSSAIs corresponding to one or more network slices or network sliceinstances to which the UE subscribed; Subscribed network slice isolationinformation (e.g. network slice isolation type/level applied to thesubscribed NSSAI and/or the subscribed NSSAI related network sliceinstance(s)); UE identifier(s) (e.g. SUPI and/or 5G-GUTI); PDU sessionID(s); and DNN.

In response to the message received from the UDM 140, the NRF 130 maytake one or more of actions. In an example action, the NRF 130 maydetermine/select AMF(s) based on one or more of the followinginformation: Requested NSSAI; Requested network slice isolationinformation received from the (R)AN 105; Subscribed NSSAI; Subscribednetwork slice isolation information received from the UDM 140; UEidentifier(s) (e.g. SUPI and/or 5G-GUTI); DNN; local operator policiesconfigured in NRF 130; and subscription information of UE configured inNRF 130 or received from the UDM 140. In an example, the NRF 130 mayselect AMF(s) which may support the fully isolated network slice(s) forthe requested NSSAI and/or subscribed NSSAI. In an example action, inresponse to the message received from the (R)AN 105, the NRF 130 maysend to the (R)AN 105 a response message (e.g. Nnrf NFDiscovery RequestResponse) comprising one or more of the following information: UEidentifier(s) (e.g. SUPI and/or 5G-GUTI); Requested NSSAI; SubscribedNSSAI; Subscribed network slice isolation information (e.g. networkslice isolation type/level applied to the subscribed NSSAI and/or thesubscribed NSSAI related network slice instance(s)); AMF (s) (e.g. IPaddress(es) or FQDN(s) of AMF(s)) that serve the requested NSSAI and/orsubscribed NSSAI; and DNN.

In response to the message received from the NRF 130, the (R)AN 105 maycontinue the registration procedure (e.g. send a registration requestmessage to an AMF selected by the NRF 130) and may send to the UE 100 aregistration accept message. In response to the message received fromthe (R)AN 105, the UE 100 may send to the (R)AN 105 a registrationcomplete message.

Example 2

In an example, an NSSF may select an AMF for the partly isolated networkslice with (R)AN shared. FIG. 15 is an example call flow diagram as peran aspect of an embodiment of the present disclosure. UE 100 may send aregistration request to a (R)AN 105 comprising an AN message. The ANmessage may comprise AN parameters and/or a RM-NAS Registration Request,wherein the RM-NAS Registration Request may comprise at least one of: aregistration type, UE identifier(s) (e.g. SUPI and/or 5G-GUTI), securityparameters, a requested NSSAI, DNN, A UE SGCN Capability, a PDU sessionstatus, PDU session(s) to be re-activated, a follow on request, or aMICO mode preference. The Requested NSSAI may comprise one or moreS-NSSAIs corresponding to one or more network slices or network sliceinstances to which the UE may register. The DNN is the data networkname, which may be equivalent to an APN the UE may access. The PDUsession status and/or PDU session(s) to be re-activated may comprise thePDU session ID(s). The UE 100 may comprise network slice isolationinformation in the registration request as specified in Example 1, andin an example, partly isolated network slice with (R)AN isolated valuemay be set by the UE 100 for the network slice isolation type (NSIT).

In response to the message received from the UE 100, the (R)AN 105, maysend to an NSSF 120 a message (e.g. AMF discovery request) to select anAMF, and the message may comprise one or more of the followinginformation received from the UE 100: Requested NSSAI; Requested networkslice isolation information (e.g. network slice isolation type/levelapplied to the requested NSSAI and/or the requested NSSAI relatednetwork slice instance(s)); UE identifier(s) (e.g. SUPI and/or 5G-GUTI);PDU session ID(s); and DNN.

In response to the message received from the (R)AN 105, the NSSF 120 maysend the UDM 140 a message (e.g. subscriber data request) to request thesubscription information of the UE 100, the message may comprise one ormore of the following information: Requested NSSAI; Requested networkslice isolation information (e.g. network slice isolation type/levelapplied to the requested NSSAI and/or the requested NSSAI relatednetwork slice instance(s)); UE identifier(s) (e.g. SUPI and/or 5G-GUTI);PDU session ID(s); and DNN.

In response to the message received from the NSSF 120, the UDM 140 maysend to the NSSF 120 a response message (e.g. subscriber data response),and the message may comprise one or more of the following information:Subscribed NSSAI and/or subscribed NSSAI related network sliceinstance(s), where the subscribed NSSAI may comprise one or moreS-NSSAIs corresponding to one or more network slices or network sliceinstances to which the UE subscribed; Subscribed network slice isolationinformation (e.g. network slice isolation type/level applied to thesubscribed NSSAI and/or the subscribed NSSAI related network sliceinstance(s)); UE identifier(s) (e.g. SUPI and/or 5G-GUTI); PDU sessionID(s); and DNN.

In response to the message received from the UDM 140, the NSSF 120 maytake one or more actions. In an example action, the NSSF 120 maydetermine/create allowed NSSAI and/or allowed NSSAI related networkslice instance(s). The NSSF 120 may determine/create the allowed NSSAIand/or allowed NSSAI related network slice instance(s) based on one ormore of the following information: Requested NSSAI; Requested networkslice isolation information received from the (R)AN 105; SubscribedNSSAI; Subscribed network slice isolation information received from theUDM 140; UE identifier(s) (e.g. SUPI and/or 5G-GUTI); DNN; localoperator policies configured in NSSF 120; and subscription informationof UE configured in NSSF 120 or received from the UDM 140. The allowedNSSAI may comprise one or more S-NSSAIs corresponding to one or morenetwork slices or network slice instances to which the UE 100 is allowedto access. In an example action, the NSSF 120 may determine/selectAMF(s) based on one or more of the following information: RequestedNSSAI; Requested network slice isolation information received from the(R)AN 105; Subscribed NSSAI; Subscribed network slice isolationinformation received from the UDM 140; UE identifier(s) (e.g. SUPIand/or 5G-GUTI); DNN; local operator policies configured in NSSF 120;and subscription information of UE configured in NSSF 120 or receivedfrom the UDM 140. In an example, the NSSF 120 may select AMF(s) whichmay support the partly isolated network slice(s) with (R)AN shared forthe allowed NSSAI and/or subscribed NSSAI. In an example action, inresponse to the message received from the (R)AN 105, the NSSF 120 maysend to the (R)AN 105 a response message (e.g. AMF discovery response)comprising one or more of the following information: UE identifier(s)(e.g. SUPI and/or 5G-GUTI); Subscribed NSSAI; Allowed NSSAI and/orallowed NS SAI related network slice instance(s); Allowed network sliceisolation information (e.g. network slice isolation type/level appliedto the allowed NSSAI and/or the allowed NSSAI related network sliceinstance(s)); AMF (s) (e.g. IP address(es) or FQDN(s) of AMF(s)) thatserve the allowed NSSAI and/or subscribed NSSAI; and DNN.

In response to the message received from the NSSF 120, the (R)AN 105 maycontinue the registration procedure (e.g. send a registration requestmessage to an AMF selected by the NSSF 120), and may send to the UE 100a registration accept message comprising one or more of the followinginformation: Allowed NSSAI and/or allowed NSSAI related network sliceinstance(s), where the allowed NSSAI may comprise one or more S-NSSAIscorresponding to one or more network slices or network slice instancesto which the UE 100 is allowed to access; and Network slice isolationinformation (e.g. network slice isolation type/level applied to theallowed NSSAI and/or the allowed NSSAI related network sliceinstance(s)). In response to the message received from the (R)AN 105,the UE 100 may send to the (R)AN 105 a registration complete message.

Example 3

In an example, an UDM may select an AMF for the partly isolated networkslice with (R)AN and AMF shared. FIG. 16 is an example call flow diagramas per an aspect of an embodiment of the present disclosure. UE 100 maysend a registration request to a (R)AN 105 comprising an AN message. TheAN message may comprise AN parameters and/or a RM-NAS RegistrationRequest, wherein the RM-NAS Registration Request may comprise at leastone of: a registration type, UE identifier(s) (e.g. SUPI and/or5G-GUTI), security parameters, a requested NSSAI, DNN, A UE SGCNCapability, a PDU session status, PDU session(s) to be re-activated, afollow on request, or a MICO mode preference. The Requested NSSAI maycomprise one or more S-NSSAIs corresponding to one or more networkslices or network slice instances to which the UE may register. The DNNis the data network name, which may be equivalent to an APN the UE mayaccess. The PDU session status and/or PDU session(s) to be re-activatedmay comprise the PDU session ID(s). The UE 100 may comprise networkslice isolation information in the registration request as specified inExample 1, and in an example, partly isolated network slice with (R)ANand AMF isolated value may be set by the UE 100 for the network sliceisolation type (NSIT).

In response to the message received from the UE 100, the (R)AN 105, maysend to an UDM 140 a message (e.g. subscriber data request) to requestthe subscription information of the UE 100. The message may comprise oneor more of the following information: Requested NSSAI; Requested networkslice isolation information (e.g. network slice isolation type/levelapplied to the requested NSSAI and/or the requested NSSAI relatednetwork slice instance(s)); UE identifier(s) (e.g. SUPI and/or 5G-GUTI);PDU session ID(s); and DNN.

In response to the message received from the (R)AN 105, the UDM 140 maytake one or more actions. In an example action, the UDM 140 maydetermine subscribed NSSAI based on the subscription information of theUE and/or the information received from the (R)AN 105. The subscribedNSSAI may comprise one or more S-NSSAIs corresponding to one or morenetwork slices or network slice instances to which the UE subscribed.The UDM 140 may determine subscribed network slice isolation information(e.g. network slice isolation type/level applied to the subscribed NSSAIand/or the subscribed NSSAI related network slice instance(s)). In anexample action, the UDM 140 may determine/select AMF(s) based on one ormore of the following information: Requested NSSAI; Requested networkslice isolation information received from the (R)AN 105; SubscribedNSSAI; Subscribed network slice isolation information; UE identifier(s)(e.g. SUPI and/or 5G-GUTI); DNN; local operator policies configured inUDM 140; and subscription information of UE configured in UDM 140. In anexample, the UDM 140 may select AMF(s) which may support the partlyisolated network slice(s) with (R)AN and AMF shared for the allowedNSSAI and/or subscribed NSSAI. In an example action, in response to themessage received from the (R)AN 105, the UDM 140 may send to the (R)AN105 a response message (e.g. subscriber data response) comprising one ormore of the following information: UE identifier(s) (e.g. SUPI and/or5G-GUTI); Subscribed NSSAI; Allowed network slice isolation information(e.g. network slice isolation type/level applied to the allowed NSSAIand/or the allowed NSSAI related network slice instance(s)); AMF (s)(e.g. IP address(es) or FQDN(s) of AMF(s)) that serve the allowed NSSAIand/or subscribed NSSAI; and DNN.

In response to the message received from the UDM 140, the (R)AN 105 maycontinue the registration procedure (e.g. send a registration requestmessage to an AMF selected by the UDM 140), and may send to the UE 100 aregistration accept message comprising one or more of the followinginformation: Allowed NSSAI and/or allowed NSSAI related network sliceinstance(s), where the allowed NSSAI may comprise one or more S-NSSAIscorresponding to one or more network slices or network slice instancesto which the UE 100 is allowed to access; and Network slice isolationinformation (e.g. network slice isolation type/level applied to theallowed NSSAI and/or the allowed NSSAI related network sliceinstance(s)). In response to the message received from the (R)AN 105,the UE 100 may send to the (R)AN 105 a registration complete message.

Example 4

In an example, an NSSF may select an AMF for partly isolated networkslice with (R)AN shared. FIG. 17 is an example call flow diagram as peran aspect of an embodiment of the present disclosure. UE 100 may send aregistration request to a (R)AN 105 comprising an AN message. The ANmessage may comprise AN parameters and/or a RM-NAS Registration Request,wherein the RM-NAS Registration Request may comprise at least one of: aregistration type, UE identifier(s) (e.g. SUPI and/or 5G-GUTI), securityparameters, a requested NSSAI, DNN, A UE SGCN Capability, a PDU sessionstatus, PDU session(s) to be re-activated, a follow on request, or aMICO mode preference. The Requested NSSAI may comprise one or moreS-NSSAIs corresponding to one or more network slices or network sliceinstances to which the UE may register. The DNN is the data networkname, which may be equivalent to an APN the UE may access. The PDUsession status and/or PDU session(s) to be re-activated may comprise thePDU session ID(s). The UE 100 may comprise network slice isolationinformation in the registration request as specified in Example 1, andin an example, partly isolated network slice with (R)AN isolated valuemay be set by the UE 100 for the network slice isolation type (NSIT).

In response to the message received from the UE 100, the (R)AN 105, maysend to an UDM 140 a message (e.g. subscriber data request) to requestthe subscription information of the UE 100, the message may comprise oneor more of the following information: Requested NSSAI; Requested networkslice isolation information (e.g. network slice isolation type/levelapplied to the requested NSSAI and/or the requested NSSAI relatednetwork slice instance(s)); UE identifier(s) (e.g. SUPI and/or 5G-GUTI);PDU session ID(s); and DNN.

In response to the message received from the (R)AN 105, the UDM 140 maysend to the (R)AN 105 a response message (e.g. subscriber dataresponse), and the message may comprise one or more of the followinginformation: Subscribed NSSAI and/or subscribed NSSAI related networkslice instance(s), where the subscribed NSSAI may comprise one or moreS-NSSAIs corresponding to one or more network slices or network sliceinstances to which the UE subscribed; Subscribed network slice isolationinformation (e.g. network slice isolation type/level applied to thesubscribed NSSAI and/or the subscribed NSSAI related network sliceinstance(s)); UE identifier(s) (e.g. SUPI and/or 5G-GUTI); PDU sessionID(s); and DNN.

In response to the message received from the UDM 140, the (R)AN 105 maysend to an NSSF 120 a message (e.g. AMF discovery request) to select anAMF, and the message may comprise the following information: RequestedNSSAI; Requested network slice isolation information received from theUE 100; Subscribed NSSAI; Subscribed network slice isolation informationreceived from the UDM 140; UE identifier(s) (e.g. SUPI and/or 5G-GUTI);PDU session ID(s); and DNN.

In response to the message received from the (R)AN 105, the NSSF 120 maytake one or more actions. In an example action, the NSSF 120 maydetermine/create allowed NSSAI and/or allowed NSSAI related networkslice instance(s). The NSSF 120 may determine/create the allowed NSSAIand/or allowed NSSAI related network slice instance(s) based on one ormore of the following information: Requested NSSAI; Requested networkslice isolation information received from the (R)AN 105; SubscribedNSSAI; Subscribed network slice isolation information received from the(R)AN 105; UE identifier(s) (e.g. SUPI and/or 5G-GUTI); DNN; localoperator policies configured in NSSF 120; and subscription informationof UE configured in NSSF 120 or received from the UDM 140. The allowedNSSAI may comprise one or more S-NSSAIs corresponding to one or morenetwork slices or network slice instances to which the UE 100 is allowedto access. In an example action, the NSSF 120 may determine/selectAMF(s) based on one or more of the following information: RequestedNSSAI; Requested network slice isolation information received from the(R)AN 105; Subscribed NSSAI; Subscribed network slice isolationinformation received from the (R)AN 105; UE identifier(s) (e.g. SUPIand/or 5G-GUTI); DNN; local operator policies configured in NSSF 120;and subscription information of UE configured in NSSF 120 or receivedfrom the UDM 140. In this example, the NSSF 120 may select AMF(s) whichmay support the partly isolated network slice(s) with (R)AN shared forthe allowed NSSAI and/or subscribed NSSAI. In an example action, inresponse to the message received from the (R)AN 105, the NSSF 120 maysend to the (R)AN 105 a response message (e.g. AMF discovery response)comprising one or more of the following information: UE identifier(s)(e.g. SUPI and/or 5G-GUTI); Subscribed NSSAI; Allowed NSSAI and/orallowed NS SAI related network slice instance(s); Allowed network sliceisolation information (e.g. network slice isolation type/level appliedto the allowed NSSAI and/or the allowed NSSAI related network sliceinstance(s)); AMF (s) (e.g. IP address(es) or FQDN(s) of AMF(s)) thatserve the allowed NSSAI and/or subscribed NSSAI; and DNN.

In response to the message received from the NSSF 120, the (R)AN 105 maycontinue the registration procedure (e.g. send a registration requestmessage to an AMF selected by the NSSF 120), and may send to the UE 100a registration accept message comprising one or more of the followinginformation: Allowed NSSAI and/or allowed NSSAI related network sliceinstance(s), where the allowed NSSAI may comprise one or more S-NSSAIscorresponding to one or more network slices or network slice instancesto which the UE 100 is allowed to access; and Network slice isolationinformation (e.g. network slice isolation type/level applied to theallowed NSSAI and/or the allowed NSSAI related network sliceinstance(s)). In response to the message received from the (R)AN 105,the UE 100 may send to the (R)AN 105 a registration complete message.

As an example, an NRF may receive from an (R)AN a first message inresponse to a wireless device registration request. The first messagemay comprise at least one of: at least one S-NSSAI associated with atleast one network slice; a user identity of a wireless device; at leastone DNN; and network slice isolation information. The NRF may select anAMF based at least on the network slice isolation information, and maysend to the (R)AN a second message comprising an IP address or an FQDNof the AMF.

As an example, the network slice isolation information may comprise oneor more of the following information: a first indicator to indicate anetwork slice of the at least one network slice is isolated from one ormore other network slices, and a network slice instance ID of thenetwork slice.

As an example, the network slice may be isolated from the one or moreother network slices, when the network slice is fully isolated or partlyisolated from the one or more other network slices; or when the networkslice is logically isolated or physically isolated from the one or moreother network slices.

As an example, a S-NSSAI of the at least one S-NSSAI is one of arequested S-NSSAI, a subscription S-NSSAI, or allowed S-NSSAI.

As an example, selecting an AMF by the NRF may be further based on theat least one S-NSSAI, at least one DNN, or the user identity.

According to various embodiments, one or more devices such as, forexample, a wireless device, off-network wireless device, a base station,a core network device, and/or the like, may be employed in a system. Oneor more of the devices may be configured to perform particularoperations or actions by virtue of having software, firmware, hardware,or a combination of them installed on the one or more of the devices,that in operation causes or cause the one or more devices to perform theactions. One or more computer programs can be configured to performparticular operations or actions by virtue of including instructionsthat, when executed by data processing apparatus, cause the apparatus toperform the actions. Embodiments of example actions are illustrated inthe accompanying figures and specification. Features from variousembodiments may be combined to create yet further embodiments.

FIG. 23 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 2310, a radio access network may receive a firstregistration request from a wireless device. At 2320, the radio accessnetwork may send a first message to a network repository function inresponse to receiving the first registration request. The first messagemay comprise at least one single network slice selection assistanceinformation of at least one network slice. The first message maycomprise network slice isolation information for the at least one singlenetwork slice selection assistance information. At 2330, the networkrepository function may select an access and mobility managementfunction based on the network slice isolation information. At 2340, theradio access network may receive a second message from the networkrepository function. The second message may comprise an Internetprotocol address of the access and mobility management function. At2350, the radio access network may send a second message to the accessand mobility management function. The second registration request may befor the first registration request.

According to an example embodiment, the first message may comprise auser identity of the wireless device. According to an exampleembodiment, the first message may comprise a user identity of thewireless device. According to an example embodiment, the first messagemay comprise at least one data network name. According to an exampleembodiment, the network slice isolation information may comprise a firstindicator to indicate a network slice of the at least one network sliceis isolated from one or more other network slices. According to anexample embodiment, the network slice isolation information may comprisea network slice instance identifier of the network slice. According toan example embodiment, the network slice may be isolated from one ormore other network slices when the network slice is fully isolated fromthe one or more other network slices. According to an exampleembodiment, the network slice may be isolated from one or more othernetwork slices when the network slice is partly isolated from the one ormore other network slices. According to an example embodiment, thenetwork slice may be isolated from one or more other network slices whenthe network slice is logically isolated from the one or more othernetwork slices. According to an example embodiment, the network slicemay be isolated from one or more other network slices when the networkslice is physically isolated from the one or more other network slices.According to an example embodiment, the at least one single networkslice selection assistance information may comprise a requested singlenetwork slice selection assistance information. According to an exampleembodiment, the at least one single network slice selection assistanceinformation may comprise a subscription single network slice selectionassistance information. According to an example embodiment, the at leastone single network slice selection assistance information may compriseallowed single network slice selection assistance information. Accordingto an example embodiment, the selection of the access and mobilitymanagement function may be further based on the at least one singlenetwork slice selection assistance information. According to an exampleembodiment, the selecting the access and mobility management functionmay be further based on at least one data network name. According to anexample embodiment, the selecting the access and mobility managementfunction may be further based on a user identity. According to anexample embodiment, the second message may comprise an Internet protocoladdress of the access and mobility management function.

According to an example embodiment, the network slice isolationinformation may comprise a network slice isolation level to indicate alevel at which the at least one network slice is isolated from one ormore other network slices. According to an example embodiment, the levelat which the at least one network slice is isolated from the one or moreother network slices may comprise a fully isolated network slice.According to an example embodiment, the fully isolated network slice maybe a network slice instance that does not share the radio access networkwith any other network slice instance. According to an exampleembodiment, the fully isolated network slice may be a network sliceinstance that does not share a core network function with any othernetwork slice instance. According to an example embodiment, the level atwhich the at least one network slice is isolated from the one or moreother network slices may comprise a partly isolated network slice withsharing of the radio access network. According to an example embodiment,the partly isolated network slice with radio access network shared maycomprise the radio access network belonging to an isolated network sliceinstance comprising a network function that can be seen from outside ofthe isolated network slice instance. According to an example embodiment,the level of the at least one network slice is isolated from one or moreother network slices may comprise a partly isolated network slice with aradio access network and access and mobility management function shared.According to an example embodiment, the partly isolated network slicewith radio access network and access and mobility management functionshared may comprise both the radio access network and access andmobility management function belonging to an isolated network sliceinstance that can be seen from the outside of the isolated network sliceinstance.

According to an example embodiment, the network repository function maysend a third message to a unified data management. The third message mayrequest subscription information of the wireless device. The thirdmessage may comprise a user identity. The third message may comprise arequested network slice selection assistance information. According toan example embodiment, further comprising, by the network repositoryfunction may receive a fourth message from the unified data managementin response to the third message. The fourth message may comprise a useridentity. The fourth message may comprise subscribed network sliceselection assistance information. According to an example embodiment,the fourth message may comprise subscribed network slice isolationinformation applied to the subscribed network slice selection assistanceinformation. According to an example embodiment, the third message maycomprise a requested network slice isolation information applied to therequested network slice selection assistance information.

FIG. 24 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 2410, a network slice selection function may receive afirst message from a radio access network in response to a wirelessdevice registration request. The first message may comprise at least onesingle network slice selection assistance information associated with atleast one network slice. The first message may comprise network sliceisolation information. At 2420, the network slice selection function mayselect an access and mobility management function based at least on thenetwork slice isolation information. At 2430, the network sliceselection function may send a second message to the radio accessnetwork. The second message may comprise an IP address. The secondmessage may comprise a fully qualified domain name of the access andmobility management function. According to an example embodiment, thenetwork slice selection function may send a third message to a unifieddata management. The third message may request subscription informationof a wireless device. The third message may comprise a user identity.The third message may comprise requested network slice selectionassistance information. According to an example embodiment, a networkrepository function may receive a fourth message from the unified datamanagement in response to the third message. The fourth message maycomprise a user identity. The fourth message may comprise subscribednetwork slice selection assistance information.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” or “one or more.” Similarly, any term thatends with the suffix “(s)” is to be interpreted as “at least one” or“one or more.” In this disclosure, the term “may” is to be interpretedas “may, for example.” In other words, the term “may” is indicative thatthe phrase following the term “may” is an example of one of a multitudeof suitable possibilities that may, or may not, be employed to one ormore of the various embodiments. If A and B are sets and every elementof A is also an element of B, A is called a subset of B. In thisspecification, only non-empty sets and subsets are considered. Forexample, possible subsets of B={cell1, cell2} are: {can }, {cell2}, and{can, ce112}. The phrase “based on” is indicative that the phrasefollowing the term “based on” is an example of one of a multitude ofsuitable possibilities that may, or may not, be employed to one or moreof the various embodiments. The phrase “in response to” is indicativethat the phrase following the phrase “in response to” is an example ofone of a multitude of suitable possibilities that may, or may not, beemployed to one or more of the various embodiments. The terms“including” and “comprising” should be interpreted as meaning“including, but not limited to.”

In this disclosure and the claims, differentiating terms like “first,”“second,” “third,” identify separate elements without implying anordering of the elements or functionality of the elements.Differentiating terms may be replaced with other differentiating termswhen describing an embodiment.

In this disclosure, various embodiments are disclosed. Limitations,features, and/or elements from the disclosed example embodiments may becombined to create further embodiments within the scope of thedisclosure.

In this specification, parameters (Information elements: IEs) maycomprise one or more objects, and one of those objects may comprise oneor more other objects. For example, if parameter (IE) N comprisesparameter (IE) M, and parameter (IE) M comprises parameter (IE) K, andparameter (IE) K comprises parameter (information element) J, then, forexample, N comprises K, and N comprises J. In an example, when one ormore messages comprise a plurality of parameters, it implies that aparameter in the plurality of parameters is in at least one of the oneor more messages, but does not have to be in one of the one or moremessages.

Many of the elements described in the disclosed Examples may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (e.g. hardware with a biological element) or acombination thereof, some of which are behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, Matlab or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLabVIEWMathScript. Additionally, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers and microprocessors are programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDsare often programmed using hardware description languages (HDL) such asVHSIC hardware description language (VHDL) or Verilog that configureconnections between internal hardware modules with lesser functionalityon a programmable device. Finally, it needs to be emphasized that theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various Examples have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the spirit and scope. In fact, after reading theabove description, it will be apparent to one skilled in the relevantart(s) how to implement alternative Examples. Thus, the present Examplesshould not be limited by any of the above described exemplary Examples.In particular, it should be noted that, for example purposes, the aboveexplanation has focused on the example(s) using 5G AN. However, oneskilled in the art will recognize that Examples of the invention may beimplemented in a system comprising one or more legacy systems or LTE.The disclosed methods and systems may be implemented in wireless orwireline systems. The features of various Examples presented in thisinvention may be combined. One or many features (method or system) ofone Example may be implemented in other Examples. A limited number ofexample combinations are shown to indicate to one skilled in the art thepossibility of features that may be combined in various Examples tocreate enhanced transmission and reception systems and methods.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposes.The disclosed architecture is sufficiently flexible and configurable,such that it may be utilized in ways other than that shown. For example,the actions listed in any flowchart may be re-ordered or optionally usedin some Examples.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A network function comprising: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the network function to: receive, from aradio access network (RAN), a message indicating: a wireless deviceidentifier of a wireless device; one or more requested network slicesrequested by the wireless device; isolation of the one or more requestednetwork slices from one or more other network slices; and access andmobility management function (AMF) discovery; send, to a unified datamanagement (UDM), a subscriber data request message indicating: thewireless device identifier of the wireless device; and the one or morerequested network slices; receive, from the UDM, a subscriber dataresponse message indicating one or more allowed network slices that thewireless device is allowed to access; determine an address of an AMF,wherein the AMF: serves the one or more allowed network slices; and doesnot serve the one or more other network slices; and send, to the RAN, anindication of the address of the AMF.
 2. The network function of claim1, wherein the message is a discovery request message.
 3. The networkfunction of claim 1, wherein the message indicates one or more singlenetwork slice selection assistance information (S-NSSAI) of the one ormore requested network slices.
 4. The network function of claim 1,wherein the message indicates a data network name (DNN) associated withthe one or more requested network slices.
 5. The network function ofclaim 1, wherein the isolation of the one or more requested networkslices from one or more other network slices comprises isolation of oneor more first network functions of the one or more requested networkslices from one or more second network functions of the one or moreother network slices.
 6. The network function of claim 1, wherein thesubscriber data request message indicates the isolation of the one ormore requested network slices from one or more other network slices. 7.The network function of claim 1, wherein the one or more allowed networkslices consist of one or more of the one or more requested networkslices.
 8. A radio access network (RAN) comprising: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the RAN to: receive, from a wirelessdevice, a registration request indicating: a wireless device identifierof the wireless device; and one or more requested network slicesrequested by the wireless device; send, to a network function, a messageindicating: the wireless device identifier of the wireless device; theone or more requested network slices requested by the wireless device;isolation of the one or more requested network slices from one or moreother network slices; and access and mobility management function (AMF)discovery; receive, from the network function, an address associatedwith an AMF, wherein the AMF: serves one or more allowed network slicesthat the wireless device is allowed to access; and does not serve theone or more other network slices; send, to the AMF associated with theaddress, the registration request; receive, from the AMF associated withthe address, a registration response; send, to the wireless device, theregistration response.
 9. The RAN of claim 8, wherein the message is adiscovery request message.
 10. The RAN of claim 8, wherein the messageindicates one or more single network slice selection assistanceinformation (S-NSSAI) of the one or more requested network slices. 11.The RAN of claim 8, wherein the message indicates a data network name(DNN) associated with the one or more requested network slices.
 12. TheRAN of claim 8, wherein the isolation of the one or more requestednetwork slices from one or more other network slices comprises isolationof one or more first network functions of the one or more requestednetwork slices from one or more second network functions of the one ormore other network slices.
 13. The RAN of claim 8, wherein theregistration response indicates acceptance of the registration request.14. The RAN of claim 8, wherein the one or more allowed network slicesconsist of one or more of the one or more requested network slices. 15.A non-transitory computer-readable medium comprising instructions that,when executed by one or more processors of a network function, cause thenetwork function to: receive, from a radio access network (RAN), amessage indicating: a wireless device identifier of a wireless device;one or more requested network slices requested by the wireless device;isolation of the one or more requested network slices from one or moreother network slices; and access and mobility management function (AMF)discovery; send, to a unified data management (UDM), a subscriber datarequest message indicating: the wireless device identifier of thewireless device; and the one or more requested network slices; receive,from the UDM, a subscriber data response message indicating one or moreallowed network slices that the wireless device is allowed to access;determine an address of an AMF, wherein the AMF: serves the one or moreallowed network slices; and does not serve the one or more other networkslices; and send, to the RAN, an indication of the address of the AMF.16. The non-transitory computer-readable medium of claim 15, wherein themessage is a discovery request message.
 17. The non-transitorycomputer-readable medium of claim 15, wherein the message indicates oneor more single network slice selection assistance information (S-NSSAI)of the one or more requested network slices.
 18. The non-transitorycomputer-readable medium of claim 15, wherein the message indicates adata network name (DNN) associated with the one or more requestednetwork slices.
 19. The non-transitory computer-readable medium of claim15, wherein the isolation of the one or more requested network slicesfrom one or more other network slices comprises isolation of one or morefirst network functions of the one or more requested network slices fromone or more second network functions of the one or more other networkslices.
 20. The non-transitory computer-readable medium of claim 15,wherein the subscriber data request message indicates the isolation ofthe one or more requested network slices from one or more other networkslices.